Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(maint) Add issue and PR auto responses #2585

Merged

Conversation

pauby
Copy link
Member

@pauby pauby commented Nov 29, 2024

Description

Add auto response messages to issues and PR's that are submitted. This will help provide an understanding of what people should expect.

Motivation and Context

There are a number of PR's being submitted that are wrong, and issues being raised where people expect the community team to do all the work. I hope this helps to address some of this (it won't fix it but every little bit helps).

How Has this Been Tested?

This is currently working over on my GitHub repository.

Screenshot (if appropriate, usually isn't needed):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Migrated package (a package has been migrated from another repository)

Checklist:

  • My code follows the code style of this repository.
  • My change requires a change to documentation (this usually means the notes in the description of a package).
  • I have updated the documentation accordingly (this usually means the notes in the description of a package).
  • I have updated the package description and it is less than 4000 characters.
  • All files are up to date with the latest Contributing Guidelines
  • The added/modified package passed install/uninstall in the Chocolatey Test Environment(https://github.com/chocolatey-community/chocolatey-test-environment/). Note that we don't support the use of any other environment.
  • The changes only affect a single package (not including meta package).

@pauby pauby requested a review from AdmiringWorm November 29, 2024 11:15
@AppVeyorBot
Copy link

✅ Package verification completed without issues. PR is now pending human review

.github/workflows/respond-to-issue.yaml Outdated Show resolved Hide resolved
.github/workflows/respond-to-issue.yaml Show resolved Hide resolved
.github/workflows/respond-to-pr.yaml Outdated Show resolved Hide resolved
.github/workflows/respond-to-pr.yaml Show resolved Hide resolved
@pauby pauby force-pushed the feat/add_auto_responses branch from 7e8efb8 to 9891cbd Compare November 29, 2024 15:10
@pauby
Copy link
Member Author

pauby commented Nov 29, 2024

@AdmiringWorm this is ready for review again. Thanks for the suggestions - 'created' is a much better option!

@AppVeyorBot
Copy link

✅ Package verification completed without issues. PR is now pending human review

@pauby pauby force-pushed the feat/add_auto_responses branch from 9891cbd to b454a8b Compare November 29, 2024 15:39
@AppVeyorBot
Copy link

✅ Package verification completed without issues. PR is now pending human review

Copy link
Member

@AdmiringWorm AdmiringWorm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I am a bit uncertain if the links to Contributing.md and Comitters.md is correct. But we can quickly change that if needed.

Copy link
Member

@AdmiringWorm AdmiringWorm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I am a bit uncertain if the links to Contributing.md and Comitters.md is correct. But we can quickly change that if needed.

@AdmiringWorm AdmiringWorm merged commit 6ce4b36 into chocolatey-community:master Nov 29, 2024
1 check passed
@AdmiringWorm
Copy link
Member

@pauby thanks for getting these workflows added. Should help with the incoming issues and PRs.

@AdmiringWorm
Copy link
Member

AdmiringWorm commented Nov 29, 2024

It looks like I misremembered the available types for issues, and PRs. I was sure I remembered using created in the past. I'll get them changed back to opened.

I'll get that updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants